-
Notifications
You must be signed in to change notification settings - Fork 90
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add DialogHeader to lab #4298
Add DialogHeader to lab #4298
Conversation
🦋 Changeset detectedLatest commit: 144a35d The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Needing QA story..?
e2f61e5
to
45a82d8
Compare
f20268c
to
8803846
Compare
47221d0
to
7d332ad
Compare
7d332ad
to
b5bef67
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks fine. Will tick once Nav reviewed this.
I think we need to talk about migration path (ad code diff vs current approach) for the user around it. Is it true that the only/major change is the additionally actions
prop? If so, when this works, I guess we're not moving this lab header to core, but rather deprecate DialogActions
in core and add actions
prop to the existing Dialog header?
No description provided.